Skip to content

Chore: Update NR Agent#1731

Open
jcountsNR wants to merge 3 commits into
github:stagedfrom
newrelic-partners:staged
Open

Chore: Update NR Agent#1731
jcountsNR wants to merge 3 commits into
github:stagedfrom
newrelic-partners:staged

Conversation

@jcountsNR
Copy link
Copy Markdown
Contributor

@jcountsNR jcountsNR commented May 15, 2026

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • I have read and followed the Guidance for submissions involving paid services.
  • My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
  • The file follows the required naming convention.
  • The content is clearly structured and follows the example format.
  • I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
  • I have run npm start and verified that README.md is up to date.
  • I am targeting the staged branch for this pull request.

Description

Some fixes to the nr custom agent and updated for several models.


Type of Contribution

  • New instruction file.
  • New prompt file.
  • New agent file.
  • New plugin.
  • New skill file.
  • New agentic workflow.
  • Update to existing instruction, prompt, agent, plugin, skill, or workflow.
  • Other (please specify):

Additional Notes


By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

Copilot AI review requested due to automatic review settings May 15, 2026 17:42
@jcountsNR jcountsNR requested a review from aaronpowell as a code owner May 15, 2026 17:42
@github-actions github-actions Bot added agent PR touches agents skill-check-error Skill validator reported errors labels May 15, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 15, 2026

🔍 Skill Validator Results

⛔ Findings need attention

Scope Checked
Skills 1
Agents 1
Total 2
Severity Count
--- ---:
❌ Errors 2
⚠️ Warnings 0
ℹ️ Advisories 0

Summary

Level Finding
[agent:New Relic Incident Response Agent] Agent name 'New Relic Incident Response Agent' does not match filename 'new-relic-incident-response.agent.md' (expected 'New Relic Incident Response Agent.agent.md').
[agent:New Relic Incident Response Agent] Agent name 'New Relic Incident Response Agent' contains invalid characters — must be lowercase alphanumeric and hyphens only.
Full validator output ```text Found 1 agent(s) ❌ [agent:New Relic Incident Response Agent] Agent name 'New Relic Incident Response Agent' does not match filename 'new-relic-incident-response.agent.md' (expected 'New Relic Incident Response Agent.agent.md'). ❌ [agent:New Relic Incident Response Agent] Agent name 'New Relic Incident Response Agent' contains invalid characters — must be lowercase alphanumeric and hyphens only. Validated 1 agent(s)

{Ansi.Red}Agent spec conformance failures — fix the errors above.{Ansi.Reset}

</details>
> **Note:** The validator returned a non-zero exit code. Please review the findings above before merge.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the New Relic incident response custom agent with expanded MCP setup guidance and a more explicit phased incident investigation workflow.

Changes:

  • Updates agent metadata for model/tool configuration.
  • Adds New Relic MCP server setup requirements and example settings.
  • Adds operating guidance for phased incident assessment, root-cause analysis, and remediation.


## MCP Server Configuration requirement

This custom agent depends on a configured New Relic MCP server. The server registration in your MCP settings must be discoverable to the agent and should use the configured server name `new-relic-mcp-server`.
Comment thread agents/new-relic-incident-response.agent.md Outdated
You have access to New Relic's MCP server tools through the users environment. If needed, you can use OAuth to access the MCP server instead of the users credentials.

# New Relic Incident Response & Debugging Agent - System Prompt
This repository should have access to information around how this application and codebase is instrumented with New Relic. You can find information on the context by using newrelic.ini directory in this repository. Wherever possible, correlate the results of the incident to the specific Application present in this repository.
- github
---
# Context
You have access to New Relic's MCP server tools through the users environment. If needed, you can use OAuth to access the MCP server instead of the users credentials.
- If your environment uses a different server name, update the tool prefixes in this agent profile to match the configured name
- If the MCP settings use `include-tags`, only tools in those tag groups will actually be exposed to the agent even if they are listed in `tools:` here
- Keep `.vscode/mcp.json` aligned with this profile when using the agent in VS Code.
- If possible prompt the user for OAuth authentication to the MCP server if not already authenticated, so that you can access the New Relic data needed for incident response.
jcountsNR and others added 2 commits May 15, 2026 12:47
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agent PR touches agents skill-check-error Skill validator reported errors

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants